Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Jan 26, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) 22.10.6 -> 22.10.10 age adoption passing confidence

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Yang-33 and others added 24 commits January 15, 2025 23:19
* Codes are generated by openapi

* Update utils.spec.ts

---------

Co-authored-by: github-actions <[email protected]>
Co-authored-by: Yuta Kasai <[email protected]>
* Codes are generated by openapi

* Update utils.spec.ts

* Update utils.spec.ts

* Update utils.spec.ts

* Update utils.spec.ts

---------

Co-authored-by: github-actions <[email protected]>
Co-authored-by: Yuta Kasai <[email protected]>
* Codes are generated by openapi

* Update utils.spec.ts

* Update utils.spec.ts

---------

Co-authored-by: github-actions <[email protected]>
Co-authored-by: Yuta Kasai <[email protected]>
@renovate renovate bot changed the title Update dependency @types/node to v22.10.10 Update dependency @types/node to v22.10.10 - autoclosed Jan 26, 2025
@renovate renovate bot closed this Jan 26, 2025
@renovate renovate bot deleted the renovate/node-22.x-lockfile branch January 26, 2025 13:10
@renovate renovate bot changed the title Update dependency @types/node to v22.10.10 - autoclosed Update dependency @types/node to v22.10.10 Jan 26, 2025
@renovate renovate bot reopened this Jan 26, 2025
@renovate renovate bot force-pushed the renovate/node-22.x-lockfile branch from 7d7447c to 293bb78 Compare January 26, 2025 13:58
@renovate
Copy link
Author

renovate bot commented Jan 26, 2025

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package.json
Post-upgrade command 'npm install --package-lock-only' has not been added to the allowed list in allowedPostUpgradeCommands
File name: package.json
Post-upgrade command 'npm install --prefix examples/echo-bot --package-lock-only' has not been added to the allowed list in allowedPostUpgradeCommands
File name: package.json
Post-upgrade command 'npm install --prefix examples/echo-bot-esm --package-lock-only' has not been added to the allowed list in allowedPostUpgradeCommands
File name: package.json
Post-upgrade command 'npm install --prefix examples/echo-bot-ts-cjs --package-lock-only' has not been added to the allowed list in allowedPostUpgradeCommands
File name: package.json
Post-upgrade command 'npm install --prefix examples/echo-bot-ts-esm --package-lock-only' has not been added to the allowed list in allowedPostUpgradeCommands
File name: package.json
Post-upgrade command 'npm install --prefix examples/kitchensink --package-lock-only' has not been added to the allowed list in allowedPostUpgradeCommands
File name: package.json
Post-upgrade command 'npm install --prefix examples/rich-menu --package-lock-only' has not been added to the allowed list in allowedPostUpgradeCommands

@renovate renovate bot force-pushed the renovate/node-22.x-lockfile branch 2 times, most recently from fb6b773 to 9ec2acb Compare January 26, 2025 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants